Systems and methods for using image data to generate vehicle operation logs

ABSTRACT

Systems and methods for generating vehicle operation logs are provided. According to certain aspects, an electronic device may receive and analyze image data depicting an individual located within a vehicle. The electronic device may also interface with a set of sensors to retrieve or access relevant data related to the operation of the vehicle, such as time and date information, location information, and other data. The electronic device may generate a vehicle operation log that associates the individual depicted in the image data with the vehicle operating parameters.

TECHNICAL FIELD

The present disclosure is directed to detecting and recording parametersassociated with vehicle operation. More particularly, the presentdisclosure is directed to systems and methods for using image data toidentify individuals within a vehicle, and generating a vehicleoperation log related to operation of the vehicle.

BACKGROUND

Individuals have been operating and traveling in vehicles as a means oftransportation for decades. With the increasing prevalence of electronicdevices and sensors, there are available more components to generatedata associated with vehicle operation. For example, vehicle sensors canmeasure or detect vehicle location, acceleration, general movement, andother information. There are existing applications that use this data tofacilitate certain functionalities. For example, vehicle operators areable to share their velocity with other vehicle operators so that theother operators may gauge certain traffic conditions.

However, there are no existing solutions for effectively and efficientlycompiling and recording certain vehicle operation parameters. Further,there are no existing solutions for accurately associating certainvehicle operators with particular vehicle operation data. Accordingly,there is an opportunity for systems and methods to leverage various datato associate vehicle operators with vehicles, and compile and recordvehicle operation data associated therewith.

SUMMARY

A computer-implemented method in an electronic device of generating avehicle operation log associated with operation of a vehicle may beprovided. The method may include receiving image data from at least oneimage sensor located within the vehicle, analyzing, by a computerprocessor, the image data to identify an operator of the vehicle,identifying a current time corresponding to approximately when the imagedata is received, detecting that the vehicle is currently in motion, andin response to detecting that the vehicle is currently in motion,generating the vehicle operation log to indicate the operator of thevehicle and the current time.

In another embodiment, a system in an electronic device for generating avehicle operation log associated with operation of a vehicle may beprovided. The system may include a memory configured to storenon-transitory computer executable instructions, and a processorconfigured to interface with the memory. The processor may be configuredto execute the non-transitory computer executable instructions to causethe processor to receive image data from at least one image sensorlocated within the vehicle, analyze the image data to identify anoperator of the vehicle, identify a current time corresponding toapproximately when the image data is received, detect that the vehicleis currently in motion, and in response to detecting that the vehicle iscurrently in motion, generate the vehicle operation log to indicate theoperator of the vehicle and the current time.

BRIEF DESCRIPTION OF THE FIGURES

FIGS. 1A and 1B depict exemplary environments within a vehicle includingvarious components configured to facilitate various functionalities, inaccordance with some embodiments.

FIG. 2 depicts an exemplary signal diagram associated with analyzingimage data to identify individuals associated with a vehicle andgenerating a vehicle operation log, in accordance with some embodiments.

FIG. 3 depicts an exemplary flow diagram associated with analyzing imagedata to identify individuals associated with a vehicle and generating avehicle operation log, in accordance with some embodiments.

FIGS. 4A and 4B depict exemplary user interfaces associated withgenerating vehicle operation logs, in accordance with some embodiments.

FIG. 5 is a block diagram of an exemplary electronic device, inaccordance with some embodiments.

DETAILED DESCRIPTION

The present embodiments may relate to, inter alia, detecting, recording,and compiling various vehicle operation data. Existing vehicle operationenvironments support the generation of various vehicle operation data.However, there is no way to properly compile the vehicle operation datawith certain associations or pairings in a meaningful manner to enablethe data to be effectively analyzed and used for subsequent applicationsor inspections. The present embodiments improve these shortcomings byeffectively and efficiently organizing the vehicle operation data forsubsequent retrieval and/or analysis.

According to certain aspects, a vehicle or an electronic device withinthe vehicle may be equipped with one or more image sensors. The imagesensor(s) may be configured to capture image data of an operator (or apassenger(s)) of the vehicle and transmit the captured image data to anelectronic device. After receiving the image data, the electronic devicemay access stored user profile data that may include physicalcharacteristics of a set of users. The electronic device may analyze thereceived image data by comparing the received image data to the storeduser profile data to identify an individual depicted in the receivedimage data, where the individual may be an operator or a passenger ofthe vehicle.

Further, the electronic device may determine or identify certain vehicleoperation parameters, including but not limited to time and/or date,location data, and route information. The electronic device may compilethe data to associate the compiled vehicle operation parameters with theindication of the individual. The electronic device may further storethe data by, for example, generating a vehicle operation log that mayindicate the individual and the compiled vehicle operation parameters.

The systems and methods therefore offer numerous benefits. Inparticular, the individual may review the vehicle operation log toreview or recall certain information, or to analyze certain informationin an attempt to make various improvements (e.g., identify a mostefficient route to work). Further, an individual, entity, or the likemay access the vehicle operation log for various purposes orapplications. For example, an insurance provider may access the vehicleoperation log and, based on the data include in the vehicle operationlog, may generate a quote for a vehicle insurance policy. For furtherexample, a parent may access the vehicle operation log to monitorvehicle travel by one or more children. It should be appreciated thatother benefits are envisioned.

The systems and methods discussed herein address a challenge that isparticular to vehicle operation. In particular, the challenge relates toa difficulty in interpreting the multiple types of data associated withoperating vehicles. This is particularly apparent with the increasingamount of vehicle sensors and types of data generated therefrom. Inconventional environments, the data is generated and reviewed withoutany sort of data correlation or log generation. In contrast, the systemsand methods automatically correlate certain types of data as the data isrecorded or generated, which results in effectively compiled data thatmay be used for various applications and interpretations. Therefore,because the systems and methods employ the collection, compiling, andstoring of data associated with vehicle, the systems and methods arenecessarily rooted in computer technology in order to overcome the notedshortcomings that specifically arise in the realm of vehicle operation.

Similarly, the systems and methods provide improvements in a technicalfield, namely, vehicle data compiling. Instead of the systems andmethods merely being performed by hardware components using basicfunctions, the systems and methods employ complex steps that go beyondthe mere concept of simply retrieving and combining data using acomputer. In particular, the hardware components capture image data,analyze the image data in combination with stored user profile data toidentify individual(s) depicted in the image data, associate variousvehicle operation parameters with the identified individual, andgenerate a vehicle operation log that may be accessed and analyzed. Thiscombination of elements further impose meaningful limits in that theoperations are applied to improve vehicle data compiling by associatingmultiple types of distinct data in a meaningful and effective way.

According to implementations, the systems and methods may support adynamic, real-time or near-real-time analysis of any captured, received,and/or detected data. In particular, the electronic device may receiveor capture image data in real-time or near real-time, and mayautomatically and dynamically analyze the captured image data bycomparing the captured image data to stored profile data. The electronicdevice may also receive or detect certain vehicle operation parametersin real-time or near-real-time, and may automatically and dynamicallyassociate and/or compile the image data and the vehicle operationparameters. In this regard, the individual indicated in the data oraccessing the data is afforded the benefit of an accurate and meaningfulcompilation of data. Further, any individual may access and analyze thedata in real-time or near-real-time to efficiently and effectivelyfacilitate any functionalities or processing.

FIG. 1A illustrates an example depiction of an interior of a vehicle 100that may include various components associated with the systems andmethods. In some scenarios, an individual 102 may operate (i.e., drive)the vehicle 100. Although the individual 102 is depicted as sitting inthe driver's seat of the vehicle 100 and operating the vehicle 100, itshould be appreciated that the individual 102 may be a passenger of thevehicle, and may sit in a front passenger seat or any of a set of rearpassenger seats. In scenarios in which the individual 102 is a passengerof the vehicle 100, another individual may operate the vehicle 100.

As depicted in FIG. 1A, the interior of the vehicle 100 may support aset of image sensors 105, 106, 107. In the particular scenario depictedin FIG. 1A, each of the image sensors 105, 107 is located near a topcorner of the interior of the vehicle 100, and the image sensor 106 islocated below a rear view minor. Although three (3) image sensors aredepicted in FIG. 1A, it should be appreciated that additional or fewerimage sensors are envisioned. Further, it should be appreciated that theimage sensors 105, 106, 107 may be disposed or located at variousalternate or additional portions of the vehicle 100, including on anexterior of the vehicle 100.

Each of the image sensors 105, 106, 107 may be configured to detect andconvey information that constitutes an image. In particular, each of theimage sensors 105, 106, 107 may generate digital image data according tothe detected information, where the digital image data may be in theform of image data and/or video data. Although not depicted in FIG. 1A,the vehicle 100 may also include one or more microphones that may bedisposed in one or more locations, where the microphones may beconfigured to capture audio data that may supplement the digital imagedata captured by the image sensors 105, 106, 107.

The vehicle 100 may also be configured with an electronic device 110configured with any combination of software and hardware components. Insome implementations, the electronic device 110 may be included as partof an on-board diagnostic (OBD) system or any other type of systemconfigured to be installed in the vehicle 100, such as an originalequipment manufacturer (OEM) system. The electronic device 110 mayinclude a set of sensors configured to detect and record varioustelematics data associated with the vehicle 100. In someimplementations, the electronic device 110 may be configured tocommunicate with (i.e., request, retrieve, or receive data from) a setof sensors disposed in other locations of the vehicle 100, such as eachof the image sensors 105, 106, 107. Further, in some implementations,the electronic device 110 itself may be equipped with one or more imagesensors.

According to embodiments, the set of sensors included in the electronicdevice 110 or otherwise configured to communicate with the electronicdevice 110 may be of various types. For example, the set of sensors mayinclude a location module (e.g., a global positioning system (GPS)chip), an accelerometer, an ignition sensor, a clock, speedometer, atorque sensor, a throttle position sensor, and/or other sensors.

FIG. 1B depicts another configuration of an interior of the vehicle 100that may include various components associated with the systems andmethods. Similar to the depiction of FIG. 1A, the depiction of FIG. 1Billustrates the individual 102 who may be an operator or passenger ofthe vehicle. The individual 102 may access and interface with anelectronic device 115 that may be located within the vehicle 100.Although FIG. 1B depicts the individual 102 holding the electronicdevice 115, it should be appreciated that the electronic device 115 maybe located within the vehicle 100 without the individual 102 contactingthe electronic device 115. For example, the electronic device 115 may besecured within a mount.

According to embodiments, the electronic device 115 may be any type ofelectronic device such as a mobile device (e.g., a smartphone). Itshould be appreciated that other types of electronic devices and/ormobile devices are envisioned, such as notebook computers, tablets,phablets, GPS (Global Positioning System) or GPS-enabled devices, smartwatches, smart glasses, smart bracelets, wearable electronics, PDAs(personal digital assistants), pagers, computing devices configured forwireless communication, and/or the like. The electronic device 115 maybe configured with at least one image sensor 120 configured to capturedigital image data, as discussed herein. The electronic device 115 mayfurther include additional sensors, such as a clock, accelerometer,location module (e.g., GPS chip), gyroscope, and/or other types ofsensors.

In some implementations, the electronic device 115 may be configured tointerface with additional components of the vehicle 100. In particular,the electronic device 115 may interface with the electronic device 110and sensors thereof, any of the image sensors 105, 106, 107, and/orother components of the vehicle 100, such as any additional sensors thatmay be disposed within the vehicle 100. Further, although not depictedin FIG. 1A or 1B, the vehicle 100 and/or each of the electronic devices110, 115 may be equipped with storage or memory capable of storingvarious data.

In operation, either of the electronic devices 110, 115 may beconfigured to receive or otherwise access image data captured by anycombination of the image sensors 105, 106, 107, 120. The electronicdevices 110, 115 may access user profile data that may be stored in thestorage or memory, and may compare the received image data to the userprofile data to identify the individual 102 who may be depicted in theimage data. The electronic devices 110, 115 may further interface withthe various sensors or other components to assess real-timeenvironmental parameters associated with operation of the vehicle 100(e.g., speed, location, route information, current time, current date).The electronic devices 110, 115 may generate a vehicle operation logthat may indicate the identified individual and may include any of thevehicle operation parameters, where the vehicle operation log may belater accessed and examined for various applications. The electronicdevices 110, 115 may also provide, in real-time, near real-time, or atanother time, the generated vehicle operation log to a third partyentity or device (e.g., an insurance provider).

According to embodiments, an individual may manually access and examinethe vehicle operation log, or a computing device may automaticallyaccess and examine the vehicle operation log, to facilitate the variousapplications. For example, an insurance provider may automaticallyanalyze the vehicle operation log to generate a vehicle insurance policyquote according to the data included in the vehicle operation log.Accordingly, the insurance provider may generate the vehicle insurancepolicy quote in real-time or near-real-time to when the electronicdevice 110, 115 generates the vehicle operation log. Further, theinsurance provider may provide the vehicle insurance policy quote to theindividual 102, such as when the individual 102 is still operating thevehicle or otherwise in real-time or near-real-time to generation of thevehicle operation log, where the individual 102 may select to purchasethe vehicle insurance policy.

FIG. 2 depicts a signal diagram 200 associated with facilitating certainfunctionalities associated with the systems and methods. The signaldiagram 200 includes a set of components that may be associated with avehicle: a clock 240 or similar component configured to identify and/ormaintain a current time and date, an electronic device 246 (such as oneof the electronic devices 110, 115 as discussed with respect to FIGS. 1Aand 1B), an image sensor 242 (such as one of the image sensors 105, 106,107, 120 as discussed with respect to FIGS. 1A and 1B), and a locationmodule 244.

The signal diagram 200 may begin when the electronic device 246optionally requests (250) image data from the image sensor 242.According to embodiments, the electronic device 246 may automaticallyrequest the image data periodically (e.g., once every ten seconds, onceevery minute, once every hour), or a user of the electronic device 246may cause the electronic device 246 to request the image data. Further,the request may include a specified amount of image data and/or aspecific time component (e.g., real-time image(s), real-time video,image(s) and/or video recorded five minutes ago). It should beappreciated that the image sensor 242 may be internal to or externalfrom the electronic device 246.

The image sensor 242 may send (252) the image data to the electronicdevice 246. In one implementation, the image sensor 242 mayautomatically send the image data to the electronic device 246 inreal-time or near real-time as the image sensor 242 captures the imagedata, and/or in response to a request from the electronic device 246. Inanother implementation, the image sensor 242 may sendpreviously-captured image data to the electronic device 246, such as ifthe image sensor 242 interfaces with some type of memory or storage. Itshould be appreciated that the image data may depict a vehicle operatoror a passenger of the vehicle.

The electronic device 246 may access (254) image profile data associatedwith one or more individuals. In embodiments, the one or moreindividuals may be registered or otherwise associated with the vehicle(e.g., one or more registered drivers of the vehicle). The electronicdevice 246 may access the image profile data from local memory or fromremote storage via a network connection. According to embodiments, theimage profile data may include a set of attributes, characteristics,and/or the like that may be related to the one or more individuals. Forexample, the image profile data may include facial recognition datarelated to relative positions, sizes, and/or shapes of the eyes, noses,cheekbones, jaws, and/or other features of the one or more individuals.

The electronic device 246 may identify (256) an individual depicted inthe image data based on an analysis of the received image data and theaccessed image profile data. According to the embodiments, theindividual depicted in the image data may be the vehicle operator or apassenger of the vehicle. In one implementation, the electronic device246 may perform a facial recognition algorithm or technique using thereceived image data to determine that the facial features of anindividual depicted in the received image data matches thosecorresponding to an individual included in the image profile data. Itshould be appreciated that other types of calculations, algorithms,comparisons, or techniques are envisioned.

The electronic device 246 may retrieve (258) the current time and/ordate from the clock 240. In an implementation, the electronic device 246may retrieve the current time and/or data in response to receiving theimage data from the image sensor, in response to identifying theindividual depicted in the image data, or in response to anothertrigger. It should be appreciated that the clock 240 may be included aspart of the electronic device 246. In an implementation, the clock 240may be a component of the vehicle, such as an on-board system of thevehicle, or as part of an auxiliary device.

The electronic device 246 may also optionally retrieve (260) locationdata from the location module 244. In embodiments, the location data maybe in the form of GPS coordinates, or other similar location data. Theelectronic device 246 may retrieve the location data at multiple pointsin time, which may indicate movement and/or a direction of travel. In animplementation, the electronic device 246 may retrieve the location datain response to receiving the image data from the image sensor, inresponse to identifying the individual depicted in the image data, or inresponse to another trigger. It should be appreciated that the locationmodule 244 may be included as part of the electronic device 246. In animplementation, the location module 244 may be a component of thevehicle, such as an on-board system of the vehicle, or as part of anauxiliary device, such as a GPS unit.

The electronic device 246 may determine (262) whether the vehicle is inmotion or otherwise operating. In an implementation, the electronicdevice 246 may determine motion or operation based on data from one ormore motion or location sensors, such as an accelerometer, a gyroscope,the location module 244, and/or another sensor. The electronic device246 may also interface with a speedometer of the vehicle to determinewhether the vehicle is in motion. In an implementation, the electronicdevice 246 may determine whether the vehicle is in motion or operatingin response to receiving the image data from the image sensor, inresponse to identifying the individual depicted in the image data, inresponse to retrieving the location data, or in response to anothertrigger. In some embodiments, the electronic device 246 may determinethat the vehicle was in motion or operating previous to making thedetermination. For example, the electronic device 246 may determine thatthe vehicle is stopped at a stop light, if the engine of the vehicle ison and the vehicle was recently in motion.

If the electronic device 246 determines that the vehicle is not inmotion (“NO”), such as if the individual is present in the vehicle butthe vehicle is not operating, then processing may end or proceed toanother functionality. In contrast, if the electronic device 246determines that the vehicle is in motion or operating (“YES”), then theelectronic device 246 may optionally determine (264) route informationassociated with operation of the vehicle. In particular, the routeinformation may include any roads, streets, or the like on which thevehicle has traveled, along with any time of operation. To determine theroute information, the electronic device 246 may interface with one ormore local components (e.g., a location module), and/or with anycomponents of the vehicle such as an on-board system. The routeinformation may correspond to a current “trip” of the vehicle, or mayinclude one or more past trips of the vehicle.

The electronic device 246 may also generate (266) a vehicle operationlog that includes at least a portion of the determined or accessedinformation. In particular, the vehicle operation log may include anidentification of the individual, an indication of whether theindividual is the operator or a passenger, a current time and/or acurrent date, a location of the vehicle, any determined routeinformation, and/or any other information. Accordingly, the vehicleoperation log may provide an accurate snapshot of operation of thevehicle that may be accessed by one or more users or entities.

FIG. 3 depicts is a block diagram of an exemplary method 300 ofgenerating a vehicle operation log. The method 300 may be facilitated byan electronic device that may be located within a vehicle orincorporated as part of the vehicle. The electronic device may supportexecution of a dedicated application that may facilitate thefunctionalities of the method 300. Further, the electronic device mayenable a user or individual (e.g., an operator of the vehicle) to makevarious selections and facilitate various functionalities.

The method 300 may begin when the electronic device receives (block 305)image data from at least one image sensor located within the vehicle. Inembodiments, the image sensor may be a component of the electronicdevice itself or may be external to the electronic device. Further, theimage data may be received in real-time or near real-time as the atleast one image sensor captures the image data. After receiving theimage data, the electronic device may access (block 310) image profiledata associated with a set of individuals. In some embodiments, the setof individuals may be registered to or otherwise associated with thevehicle. Further, the image profile data may indicate physicalcharacteristics (e.g., facial features) of the corresponding set ofindividuals.

The electronic device may compare (block 315) the image data to theimage profile data. In one implementation, the electronic device mayperform a facial recognition analysis using the image data and the imageprofile data. It should be appreciated that alternate or additionalanalyses, techniques, calculations, algorithms, or the like areenvisioned. The electronic device may determine (block 320) whether thevehicle operator is identified from the comparison conducted in block315. If the vehicle operator is not identified (“NO”), processing mayreturn to block 305 at which additional image data may be received, orprocessing may end or proceed to other functionality.

In contrast, if the vehicle operator is identified (“YES”), theelectronic device may determine (block 325) whether the vehicle isoperating. In particular, the electronic device may determine whetherthe vehicle is operating using various sensor or other operatingparameters of the vehicle. For example, the electronic device mayreceive location data, acceleration data, sensor data from an ignitionof the vehicle, or other data that may indicate whether the vehicle isoperating. Generally, the electronic device may consider the vehicle tobe operating if the engine of the vehicle is activated or “ON”, and/orif the vehicle is in motion.

If the vehicle is not operating (“NO”), processing may return to block305 at which additional image data may be received, or processing mayend or proceed to other functionality. In contrast, if the vehicle isoperating (“YES”), the electronic device may identify (block 330) acurrent time and/or a current date. In particular, the electronic devicemay interface with an integrated or external clock component to accessthe current time and/or the current date. Further, the electronic devicemay identify (block 335) a current location. In particular, theelectronic device may interface with an integrated location module(e.g., a GPS chip) or an external location module (e.g., an on-board GPSsystem of the vehicle) to access the current location. It should beappreciated that the electronic device may identify the current time,the current date, and/or the current location in response to receivingthe image data of block 305, or at any other point of the method 300.

The electronic device may determine (block 340) route information basedat least in part of the location identified in block 335. In particular,the electronic device may identify any roadways on which the vehicle hasoperated. The route information may account for varied time periods,including time periods prior to the image data being received. Theelectronic device may generate (block 345) a vehicle operation log thatmay include any of the determined or identified data. In particular, thevehicle operation log may include an indication of the vehicle operator,a current time, a current date, a current location, route information,and/or any other data.

FIGS. 4A and 4B illustrate exemplary interfaces associated withgenerating a vehicle operation log using detected or determined vehicleoperation parameters. An electronic device (e.g., a mobile device, suchas a smartphone) may be configured to display the interfaces and/orreceive selections and inputs via the interfaces, where the electronicdevice may be associated with an operator of a vehicle, or may beintegrated into the vehicle. For example, a dedicated application thatis configured to operate on the electronic device may display theinterfaces. It should be appreciated that the interfaces are merelyexemplary and that alternative or additional content is envisioned.

FIG. 4A illustrates an interface 450 associated with the identificationof an individual depicted in image data. The interface 450 may includean information box 451 that identifies the individual (as shown: JohnDoe) and the vehicle (as shown: 2015 SUV). In embodiments, theelectronic device may identify the individual and the vehicle usingimage data received when the individual is operating the vehicle. Theinterface 450 may include a “CANCEL” selection 452 that enables anaccessing user to select to dismiss the interface 450 and a “NEXT”selection 453 that enables an accessing user to select to proceed to asubsequent interface.

FIG. 4B illustrates an additional interface 455 associated with avehicle operation log. In some embodiments, the electronic device maydisplay the additional interface 455 in response to the user selectingthe “NEXT” selection 453. The interface 455 indicates that a vehicle logentry has been created, where the vehicle log entry may include a set ofinformation 456. As illustrated in FIG. 4B, the set of information 456may include a vehicle operator name (as shown: John Doe), the vehicle(as shown: 2015 SUV), a date (as shown: September 1), a time ofoperation (as shown: 08:45-09:42 AM), and a route (as shown: 190/94 toChicago Loop). It should be appreciated that the interface 455 mayinclude alternate or additional information. The interface 455 may alsoinclude an “OKAY” selection 457 that enables the user to select todismiss the interface 455.

FIG. 5 illustrates a diagram of an exemplary mobile or other electronicdevice 510 (such as one of the electronic devices 110, 115 as discussedwith respect to FIG. 1) in which the functionalities as discussed hereinmay be implemented. It should be appreciated that the electronic device510 may be configured to be transported in a vehicle and/or connect toan on-board telematics platform of the vehicle, as discussed herein.Further, it should be appreciated that the electronic device 510 may beintegrated into an on-board system of the vehicle.

The electronic device 510 may include a processor 572 as well as amemory 578. The memory 578 may store an operating system 579 capable offacilitating the functionalities as discussed herein as well as a set ofapplications 575 (i.e., machine readable instructions). For example, oneof the set of applications 575 may be an image processing application590 configured to analyze image data to identify individuals depicted inthe image data, and a log generation application 591 configured tointerface with sensors and generate vehicle operation logs that mayinclude various vehicle operation parameters. It should be appreciatedthat one or more other applications 592 are envisioned.

The processor 572 may interface with the memory 578 to execute theoperating system 579 and the set of applications 575. According to someembodiments, the memory 578 may also include profile data 580 that mayinclude data associated with a set of individuals associated with avehicle. In some implementations, the image processing application 590may interface with the profile data 580 to retrieve appropriate profiledata and compare the profile data to received image data. The memory 578may include one or more forms of volatile and/or non-volatile, fixedand/or removable memory, such as read-only memory (ROM), electronicprogrammable read-only memory (EPROM), random access memory (RAM),erasable electronic programmable read-only memory (EEPROM), and/or otherhard drives, flash memory, MicroSD cards, and others.

The electronic device 510 may further include a communication module 577configured to communicate data via one or more networks 520. Accordingto some embodiments, the communication module 577 may include one ormore transceivers (e.g., WWAN, WLAN, and/or WPAN transceivers)functioning in accordance with IEEE standards, 3GPP standards, or otherstandards, and configured to receive and transmit data via one or moreexternal ports 576. Further, the communication module 577 may include ashort-range network component (e.g., an RFID reader) configured forshort-range network communications. For example, the communicationmodule 577 may receive, via the network 520, image data from a set ofimage sensors. For further example, the communication module 577 maytransmit data to and receive data from a remote insurance provider viathe network 520.

The electronic device 510 may further include a set of sensors 584. Theprocessor 572 and the set of applications 575 may interface with the setof sensors 584 to retrieve and process the corresponding sensor data.The set of sensors 584 may include, for example, a location module, anaccelerometer, a gyroscope, one or more image sensors, and/or the like.In one particular implementation, the log generation application 591 mayuse various data from the set of sensors 584 to generate vehicleoperation logs.

The electronic device 510 may further include a user interface 581configured to present information to a user and/or receive inputs fromthe user. As shown in FIG. 5, the user interface 581 may include adisplay screen 582 and I/O components 583 (e.g., ports, capacitive orresistive touch sensitive input panels, keys, buttons, lights, LEDs,speakers, microphones). According to some embodiments, the user mayaccess the electronic device 510 via the user interface 581 to reviewinformation and/or perform other functions. In some embodiments, theelectronic device 510 may perform the functionalities as discussedherein as part of a “cloud” network or may otherwise communicate withother hardware or software components within the cloud to send,retrieve, or otherwise analyze data.

In general, a computer program product in accordance with an embodimentmay include a computer usable storage medium (e.g., standard randomaccess memory (RAM), an optical disc, a universal serial bus (USB)drive, or the like) having computer-readable program code embodiedtherein, wherein the computer-readable program code may be adapted to beexecuted by the processor 572 (e.g., working in connection with theoperating system 579) to facilitate the functions as described herein.In this regard, the program code may be implemented in any desiredlanguage, and may be implemented as machine code, assembly code, bytecode, interpretable source code or the like (e.g., via C, C++, Java,Actionscript, Objective-C, Javascript, CSS, XML). In some embodiments,the computer program product may be part of a cloud network ofresources.

Although the following text sets forth a detailed description ofnumerous different embodiments, it should be understood that the legalscope of the invention may be defined by the words of the claims setforth at the end of this patent. The detailed description is to beconstrued as exemplary only and does not describe every possibleembodiment, as describing every possible embodiment would beimpractical, if not impossible. One could implement numerous alternateembodiments, using either current technology or technology developedafter the filing date of this patent, which would still fall within thescope of the claims.

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationsmay be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component may beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Additionally, certain embodiments are described herein as includinglogic or a number of routines, subroutines, applications, orinstructions. These may constitute either software (e.g., code embodiedon a non-transitory, machine-readable medium) or hardware. In hardware,the routines, etc., are tangible units capable of performing certainoperations and may be configured or arranged in a certain manner. Inexample embodiments, one or more computer systems (e.g., a standalone,client or server computer system) or one or more hardware modules of acomputer system (e.g., a processor or a group of processors) may beconfigured by software (e.g., an application or application portion) asa hardware module that operates to perform certain operations asdescribed herein.

In various embodiments, a hardware module may be implementedmechanically or electronically. For example, a hardware module maycomprise dedicated circuitry or logic that may be permanently configured(e.g., as a special-purpose processor, such as a field programmable gatearray (FPGA) or an application-specific integrated circuit (ASIC)) toperform certain operations. A hardware module may also compriseprogrammable logic or circuitry (e.g., as encompassed within ageneral-purpose processor or other programmable processor) that may betemporarily configured by software to perform certain operations. Itwill be appreciated that the decision to implement a hardware modulemechanically, in dedicated and permanently configured circuitry, or intemporarily configured circuitry (e.g., configured by software) may bedriven by cost and time considerations.

Accordingly, the term “hardware module” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired), or temporarilyconfigured (e.g., programmed) to operate in a certain manner or toperform certain operations described herein. Considering embodiments inwhich hardware modules are temporarily configured (e.g., programmed),each of the hardware modules need not be configured or instantiated atany one instance in time. For example, where the hardware modulescomprise a general-purpose processor configured using software, thegeneral-purpose processor may be configured as respective differenthardware modules at different times. Software may accordingly configurea processor, for example, to constitute a particular hardware module atone instance of time and to constitute a different hardware module at adifferent instance of time.

Hardware modules may provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules may be regarded as being communicatively coupled. Where multipleof such hardware modules exist contemporaneously, communications may beachieved through signal transmission (e.g., over appropriate circuitsand buses) that connect the hardware modules. In embodiments in whichmultiple hardware modules are configured or instantiated at differenttimes, communications between such hardware modules may be achieved, forexample, through the storage and retrieval of information in memorystructures to which the multiple hardware modules have access. Forexample, one hardware module may perform an operation and store theoutput of that operation in a memory device to which it may becommunicatively coupled. A further hardware module may then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware modules may also initiate communications with input oroutput devices, and may operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented modulesthat operate to perform one or more operations or functions. The modulesreferred to herein may, in some example embodiments, compriseprocessor-implemented modules.

Similarly, the methods or routines described herein may be at leastpartially processor-implemented. For example, at least some of theoperations of a method may be performed by one or more processors orprocessor-implemented hardware modules. The performance of certain ofthe operations may be distributed among the one or more processors, notonly residing within a single machine, but deployed across a number ofmachines. In some example embodiments, the processor or processors maybe located in a single location (e.g., within a home environment, anoffice environment, or as a server farm), while in other embodiments theprocessors may be distributed across a number of locations.

The performance of certain of the operations may be distributed amongthe one or more processors, not only residing within a single machine,but deployed across a number of machines. In some example embodiments,the one or more processors or processor-implemented modules may belocated in a single geographic location (e.g., within a homeenvironment, an office environment, or a server farm). In other exampleembodiments, the one or more processors or processor-implemented modulesmay be distributed across a number of geographic locations.

Unless specifically stated otherwise, discussions herein using wordssuch as “processing,” “computing,” “calculating,” “determining,”“presenting,” “displaying,” or the like may refer to actions orprocesses of a machine (e.g., a computer) that manipulates or transformsdata represented as physical (e.g., electronic, magnetic, or optical)quantities within one or more memories (e.g., volatile memory,non-volatile memory, or a combination thereof), registers, or othermachine components that receive, store, transmit, or displayinformation.

As used herein any reference to “one embodiment” or “an embodiment”means that a particular element, feature, structure, or characteristicdescribed in connection with the embodiment may be included in at leastone embodiment. The appearances of the phrase “in one embodiment” invarious places in the specification are not necessarily all referring tothe same embodiment.

The terms “insurer,” “insuring party,” and “insurance provider” are usedinterchangeably herein to generally refer to a party or entity (e.g., abusiness or other organizational entity) that provides insuranceproducts, e.g., by offering and issuing insurance policies. Typically,but not necessarily, an insurance provider may be an insurance company.

As used herein, the terms “comprises,” “comprising,” “may include,”“including,” “has,” “having” or any other variation thereof, areintended to cover a non-exclusive inclusion. For example, a process,method, article, or apparatus that comprises a list of elements is notnecessarily limited to only those elements but may include otherelements not expressly listed or inherent to such process, method,article, or apparatus. Further, unless expressly stated to the contrary,“or” refers to an inclusive or and not to an exclusive or. For example,a condition A or B is satisfied by any one of the following: A is true(or present) and B is false (or not present), A is false (or notpresent) and B is true (or present), and both A and B are true (orpresent).

In addition, use of the “a” or “an” are employed to describe elementsand components of the embodiments herein. This is done merely forconvenience and to give a general sense of the description. Thisdescription, and the claims that follow, should be read to include oneor at least one and the singular also may include the plural unless itis obvious that it is meant otherwise.

This detailed description is to be construed as examples and does notdescribe every possible embodiment, as describing every possibleembodiment would be impractical, if not impossible. One could implementnumerous alternate embodiments, using either current technology ortechnology developed after the filing date of this application.

What is claimed is:
 1. A computer-implemented method in an electronicdevice of generating a vehicle operation log associated with operationof a vehicle, the method comprising: receiving, at a first time, firstimage data from at least one image sensor, wherein the at least oneimage sensor is located within the vehicle; receiving, at a second timeafter the first time, second image data from the at least one imagesensor; analyzing, by a computer processor, the first image data and thesecond image data to identify an operator of the vehicle; in response toidentifying the operator of the vehicle: identifying a current timecorresponding to approximately when the second image data is received,detecting that the vehicle is operating, and retrieving, from a locationmodule, location data indicating a location of the vehicle at thecurrent time; determining, from the location data, route informationassociated with operation of the vehicle, the route informationidentifying a set of roadways on which the vehicle has operated;generating the vehicle operation log to indicate the operator of thevehicle, the current time, and the route information; analyzing, at athird time after the second time, the route information included in thevehicle operation log to identify an efficient route; and displaying, ina user interface, an interface indicating the vehicle operation log, theinterface identifying, concurrently, (i) the operator of the vehicle,(ii) the vehicle, and (iii) at least a portion of the route information.2. The computer-implemented method of claim 1, wherein receiving thefirst image data and the second image data comprises: receiving thefirst image data and the second image data from the at least one imagesensor included in the electronic device.
 3. The computer-implementedmethod of claim 1, wherein analyzing the first image data and the secondimage data to identify the operator of the vehicle comprises: accessingimage profile data associated with the operator of the vehicle; andcomparing the first image data and the second image data to the imageprofile data to determine that the operator of the vehicle is depictedin the first image data and the second image data.
 4. Thecomputer-implemented method of claim 3, wherein comparing the firstimage data and the second image data to the image profile datacomprises: performing a facial recognition analysis using the firstimage data, the second image data, and the image profile data; and basedon a result of the facial recognition analysis, determining that theoperator of the vehicle is depicted in the first image data and thesecond image data.
 5. The computer-implemented method of claim 1,wherein identifying the current time comprises: identifying the currenttime and a current date; and wherein generating the vehicle operationlog comprises: generating the vehicle operation log to indicate theoperator of the vehicle, the current time, the route information, andthe current date.
 6. The computer-implemented method of claim 1, whereindetecting that the vehicle is operating comprises: retrieving thelocation data from the location module of the electronic device; anddetermining, from the location data, that the vehicle is currently inmotion.
 7. The computer-implemented method of claim 1, wherein detectingthat the vehicle is operating comprises: receiving, from an on-boardsensor of the vehicle, an indication that the vehicle is in motion.
 8. Asystem in an electronic device for generating a vehicle operation logassociated with operation of a vehicle, comprising: a location moduleconfigured to generate location data; a user interface; a memoryconfigured to store non-transitory computer executable instructions; anda processor configured to interface with the memory, the locationmodule, and the user interface, wherein the processor is configured toexecute the non-transitory computer executable instructions to cause theprocessor to: receive, at a first time, first image data from at leastone image sensor located within the vehicle, receive, at a second timeafter the first time, second image data from the at least one imagesensor, analyze the first image data and the second image data toidentify an operator of the vehicle, in response to identifying theoperator of the vehicle: identify a current time corresponding toapproximately when the second image data is received, detect that thevehicle is operating, and retrieve, from the location module, thelocation data indicating a location of the vehicle at the current time,determine, from the location data, route information associated withoperation of the vehicle, the route information identifying a set ofroadways on which the vehicle has operated, generate the vehicleoperation log to indicate the operator of the vehicle, the current time,and the route information, analyze, at a third time after the secondtime, the route information included in the vehicle operation log toidentify an efficient route, and cause the user interface to display aninterface indicating the vehicle operation log, the interfaceidentifying, concurrently, (i) the operator of the vehicle, (ii) thevehicle, and (iii) at least a portion of the route information.
 9. Thesystem of claim 8, wherein to receive the first image data and thesecond image data, the processor is configured to: receive the firstimage data and the second image data from the at least one image sensorincluded in the electronic device.
 10. The system of claim 8, wherein toanalyze the first image data and the second image data to identify theoperator of the vehicle, the processor is configured to: access imageprofile data associated with the operator of the vehicle, and comparethe first image data and the second image data to the image profile datato determine that the operator of the vehicle is depicted in the firstimage data and the second image data.
 11. The system of claim 10,wherein to compare the first image data and the second image data to theimage profile data, the processor is configured to: perform a facialrecognition analysis using the first image data, the second image data,and the image profile data, and based on a result of the facialrecognition analysis, determine that the operator of the vehicle isdepicted in the first image data and the second image data.
 12. Thesystem of claim 8, wherein to identify the current time the processor isconfigured to: identify the current time and a current date; and whereinto generate the vehicle operation log, the processor is configured to:generate the vehicle operation log to indicate the operator of thevehicle, the current time, the route information, and the current date.13. The system of claim 8, wherein to detect that the vehicle isoperating, the processor is configured to: retrieve the location datafrom the location module, and determine, from the location data, thatthe vehicle is currently in motion.
 14. The system of claim 8, whereinto detect that the vehicle is operating, the processor is configured to:receive, from an on-board sensor of the vehicle, an indication that thevehicle is in motion.